Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0993

reference: 256-tree-1
name: 0993
tree-preservation-order: undefined
256-tpo-1
uprn
address-text
point: POINT (-0.935643 50.859152)
geometry: MULTIPOLYGON (((-0.935600 50.859148,-0.935602 50.859156,-0.935608 50.859163,-0.935617 50.859169,-0.935629 50.859173,-0.935642 50.859175,-0.935655 50.859174,-0.935667 50.859170,-0.935677 50.859164,-0.935683 50.859157,-0.935685 50.859148,-0.935684 50.859140,-0.935678 50.859132,-0.935668 50.859126,-0.935657 50.859122,-0.935643 50.859121,-0.935630 50.859122,-0.935618 50.859126,-0.935609 50.859132,-0.935603 50.859139,-0.935600 50.859148)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL